Error codes produced through
network operations in Director versions 6 through
MX The following is a list of the most
common network related errors reported to Lingo in
both Shockwave and Director. These error codes
will be returned when accessing information via
the netError() or
netError(netID) functions.
The netError is a function
that determines whether an error has occurred in a
network operation and, if so, returns an error
number corresponding to an error message. If the
operation was successful, this function returns a
code indicating that everything is okay ("OK"). If
no background loading operation has started, or if
the operation is in progress, this function
returns an empty string. For more information see
netError in the Lingo Dictionary
Lingo Network Errors
Error |
Description |
0 |
Everything is fine.
|
1 |
Occurs
when the local path points to a directory which
doesn't exist |
4
|
Bad MOA Class. This generally means the
required network Xtras are improperly installed,
or not installed at all. Note: This can
occur with non-network Xtras as
well. |
5 |
Bad MOA
Interface. Same as Bad MOA Class in symptoms and
remedies. |
6 |
This
alert can be achieved by using an URL which
Shockwave does not
support. |
20 |
Internal error. Returned by netError() in
Shockwave if the browser detected a network or
internal error. |
900 |
File to be written to is
read-only |
903 |
Disk is full. |
905 |
Bad filespec |
2018 |
postNetText error usually happens when
you use postNetText with the parameters in
the URL. M.Kloss recommends this syntax to avoid
2018: pNetID = postNetText(myURL,
myParamPropList) |
4144 |
Failed network operation
|
4145 |
Failed network operation
|
4146 |
Connection could not be established with
the remote host |
4149 |
Data supplied by the server was in an
unexpected format |
4150 |
Unexpected early closing of
connection |
4154 |
Operation could not be completed due to
timeout. |
4155 |
Not enough memory available to complete
the transaction |
4156 |
Protocol reply to request indicates an
error in the reply |
4157 |
Transaction failed to be
authenticated |
4159 |
Invalid URL |
4164 |
Could not create a
socket |
4165 |
Requested Object could not be found (URL
may be incorrect) |
4166 |
Generic proxy failure |
4167 |
Transfer was intentionally interrupted by
client |
4242 |
Download stopped by
netAbort(url) |
4836 |
Download stopped for an unknown reason.
May have been a network error, or the download
may have been abandoned |
4144 |
Failed network operation |
4145 |
Failed network operation |
4146 |
Connection could not be established with
the remote host |
4147 |
Failed network operation |
4148 |
Failed network operation |
4149 |
Data supplied by the server was in an
unexpected format |
4150 |
Unexpected early closing of
connection |
4151 |
Failed network operation |
4152 |
Data returned is truncated This may occur
when using a ? character at the end of a URL (T.
Schussler) |
4153 |
Failed network operation |
4154 |
Operation could not be completed due to
timeout |
4155 |
Not enough memory available to complete
the transaction |
4157 |
Transaction failed to be
authenticated |
4159 |
Invalid URL |
4160 |
Failed network operation |
4161 |
Failed
network operation |
4162 |
Failed network operation |
4163 |
Failed network
operation |
4164 |
Could not create a
socket |
4165 |
Requested
Object could not be found (URL may be
incorrect) |
4166 |
Generic proxy failure |
4167 |
Transfer
was intentionally interrupted by
client |
4168 |
Failed network operation |
4240 |
The
network xtras weren't initialized properly.
(Lewis Francis) |
4242 |
Download stopped by
netAbort(url) |
4836 |
Download
stopped for an unknown reason. May have been
a network error, or the download may have
been
abandoned. |
For a downloadable sample file implementing
the netError function see "How
do I use preLoadNetThing?" (TechNote
14595)
|